-
Notifications
You must be signed in to change notification settings - Fork 778
[WIP] Move to Java 11 as the minimum version to anticipate Lucene #3098
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
lgtm, fwiw - I personally still use tomcat + jdk8 I am not sure how much testing went into jdk11 and tomcat |
I'm using the docker image which runs on jdk11 in production and haven't seen any problems. On my computer I use jdk12 to run opengrok and it just worked, but I haven't been very active recently to test it properly. |
The instance I maintain internally is still on JDK 8 + Tomcat 8 and it might be a bit of a hurdle to jump to JDK 11 (due to Solaris x86 Java support - https://www.oracle.com/java/technologies/javase/products-doc-jdk11certconfig.html) however I feel going to JDK 11 as it is the next LSU is the way to go (JDK 14 deprecates even Solaris/SPARC anyway - https://bugs.openjdk.java.net/browse/JDK-8231554). |
I have been using JDK 11 on Ubuntu for all my local OpenGrok work for quite a while, no problems there. |
1979354
to
97786a3
Compare
needs rebase otherwise this is good to go from my point of view. |
Maddeningly after much trial and error I never got the windows build to work on this branch. I checked now on Windows 10 20xx and a different set of errors occurs. So 🤮 |
I see that the Suggester tests are failing currently. Perhaps this needs the changes in #3207 ? |
Rebased and also included a commit for Java 14 Javadoc fixes when I was trying to resolve the build on Windows (with no success) |
I see that Windows build passed in Travis. Is OpenGrok + JDK8 working on Windows 10 20xx properly? Travis does not seem to support this version so basically any change can cause the build failure on this OS and we would be blind to it. @vladak Cannot we wave it off? I think this is definitely a needed step. |
Looks like the Windows version used for Travis build is 'windows server 2019'. Personally I am fine with whatever Windows version Travis runs on. I see the Linux/macOS checks failed because of failed download. Unfortunately I cannot restart these sub-builds, will run the build as myself. |
Lucene 9.0.0 has updated its System Requirements with LUCENE-8738: Move to Java 11 as minimum Java version. (Adrien Grand, Uwe Schindler) Also: * Update jacoco to get Java 11 support. * Fix name as "Linux + OpenJDK 11" to match jdk setting. * Expand wildcard which will be needed for Java 14.
Still keeping java12plus-11-release
Also, don't bother with </p>
Unexpected coverage reduction of -11.4%. Not sure if due to intermittent build failure. Rebased to try again. |
I restarted the builds in my branch and this time it is macOS build that is failing with:
I think this is hitting #2528 due to the Xcode version bump. |
The last macOS build was successful. The Linux failed because of a network problem. So, there is nothing that would be blocking this. |
Pulled the latest branch and macOS build still fails due to setuptools vs. certificates. |
Let's see if this holds up. |
will update the wikis with the new Java version. |
Upcoming Lucene 9.0.0 has updated its System Requirements with LUCENE-8738: Move to Java 11 as minimum Java version.
This is a patch to try a revised configuration to move OpenGrok to 11 too.